Gateway Rules
Compliance – Gateway Response Rules
This module allows HelloMe Money’s compliance and fraud risk team to configure custom rules that respond to risk signals from external payment gateways, such as:
- World
- PayCross
- Trust Payment
These gateways return security validation results like:
- 3DS (3D Secure) – Did the user complete authentication?
- AVS (Address Verification Service) – Does the cardholder's address match?
- Risk Score – How suspicious is the transaction?
🛡️ Purpose
The Gateway Response Rules module enables HelloMe to apply its own decision-making logic based on these responses. Instead of accepting the gateway result as-is, the system uses internal rules to allow, block, or hold a transaction.
✅ Example Use Cases
- ❌ If AVS fails and country is Nigeria, block the transaction.
- ✅ If 3DS passes and risk level is low, allow the transaction.
This ensures more intelligent and localized fraud prevention policies across gateway providers.
1. Click this dropdown to select gateway
2. Click here.
➕ Add Response Setting
Clicking "Add Response Setting" opens a form for configuring new rules tied to a specific payment gateway.
🔧 Fields & Configuration
| Field | Description |
|---|---|
| Gateway | Dropdown to select the applicable payment gateway (e.g., World, PayCross) |
| Rule Types | Choose rule category: 3DS, AVS, or Risk |
| Enable | Toggle to activate or deactivate the rule |
| Possible Matches | Define the response patterns that trigger the rule (e.g., AVS mismatch codes) |
| Exceptions | List of countries where the rule should not apply |
| Select Countries | Specify countries or regions where the rule should apply (optional) |
🔍 Each rule type is configured independently, allowing fine-grained control by region or response type.
✅ Use Cases
- Apply dynamic fraud rules per gateway
- Enforce localized risk policies (e.g., stricter AVS for certain countries)
- Strengthen 3DS and AVS security compliance across different geographies
3. Click "Save changes"
